feat(base44-sandbox): add cloud-sandbox remote-dev skill flavor - #121

Align the backend-function test fixtures and specs with the canonical
entry.ts convention (matching base44/skills#121): rename the config-based
fixtures' index.ts entry files to entry.ts, update their function.jsonc
"entry" fields, and update all specs that referenced index.ts as a function
entry/path (project, function-config, function-schema, functions deploy/
list/pull, logs).

The CLI's own docs (docs/resources.md) and source already use entry.ts; this
removes the stale index.ts examples from fixtures. Config-based discovery
still supports an arbitrary entry filename — when we document/support that
explicitly we'll add a dedicated index.ts example + test back.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(cli): sandbox + projectless connectors remote-dev commands

Rebased onto main and aligned with the projectless app-id mechanism added
in #541: --app-id is a global program option (bound to BASE44_APP_ID), and
requireAppContext commands resolve it through the lifecycle
(ensureAppContext -> initAppContext), so commands no longer need a bespoke
resolver. Dropped the parallel cli/utils/app-id.ts and the per-command
--app-id options from the earlier iteration.

Sandbox (new `base44 sandbox <tool>`, wraps apper #11608 sandbox-bridge):
- getSandboxClient(appId) + core/resources/sandbox {schema,api}
- list-directory/read-file/write-file/edit-file/grep/run-command/release,
  JSON-first stdout; write/edit payloads via flag or stdin (verbatim)
- commands use the default app-context lifecycle and read getAppContext().id

Connectors:
- new `connectors initiate --integration-type <type> [--scopes <s...>]`:
  initializes the connector and starts its OAuth flow; prints the URL
  (agent/non-interactive friendly), opens browser + polls when interactive
- pull/push work projectless: when the app context has no projectRoot
  (explicit --app-id/BASE44_APP_ID) they use ./connectors (--dir override);
  otherwise the linked project's connectors dir
- list-available already works projectless via the lifecycle (unchanged)

Tests: sandbox.spec.ts (9), connectors_initiate.spec.ts (6), projectless
cases for connectors pull/list-available. README updated. typecheck/lint/
knip clean. Pre-existing dev/exec spec failures are environment-dependent
(deno/network) and reproduce on clean main.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* test(cli): normalize function fixtures to entry.ts

Align the backend-function test fixtures and specs with the canonical
entry.ts convention (matching base44/skills#121): rename the config-based
fixtures' index.ts entry files to entry.ts, update their function.jsonc
"entry" fields, and update all specs that referenced index.ts as a function
entry/path (project, function-config, function-schema, functions deploy/
list/pull, logs).

The CLI's own docs (docs/resources.md) and source already use entry.ts; this
removes the stale index.ts examples from fixtures. Config-based discovery
still supports an arbitrary entry filename — when we document/support that
explicitly we'll add a dedicated index.ts example + test back.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(cli): request sandbox:write scope in device login

The sandbox-bridge mutating tools (write/edit/run-command) require the
sandbox:write OAuth scope, which is deliberately kept out of the backend's
DEFAULT_SCOPE so shell access is never granted silently. Request it
explicitly in the device-code flow alongside apps:read/apps:write so
`base44 sandbox ...` works after login.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(cli): hint to re-login when sandbox returns 403

A token issued before sandbox support (or without the sandbox:write scope)
gets a 403 from the sandbox-bridge endpoints. Augment forbidden responses
from sandbox commands with a hint to run 'base44 login' again to grant
sandbox access, while preserving the server's original error/hints.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(cli): only hint re-login on a genuine missing-sandbox-scope error

The previous blanket 403 hint was wrong: the HTTP sandbox-bridge endpoints
the CLI calls authorize via the platform JWT + app-admin and do NOT enforce
sandbox:write (that check is MCP-only). Their 403s — feature-flag-off,
blocked app, view-only, wrong app type — are generic and not fixed by
re-login.

Detect the scope rejection specifically by matching the response wording
("sandbox:write" / "granting sandbox access", as emitted by the scope check)
instead of any 403, so the re-login hint only appears when it would actually
help. Added a test asserting a generic 403 (view-only) does NOT get the hint.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(cli): add global --json flag for machine-readable output

Add `--json` as a global program option (like --app-id) instead of a
per-command flag. The lifecycle centralizes the behavior:

- index.ts forces non-interactive wiring when --json is present, so the
  clack spinner and logs go to stderr.
- CLIContext gains `jsonMode`; Base44Command skips the clack framing and
  routes the status line to stderr, keeping stdout a pure JSON document.

Any command that sets RunCommandResult.stdout now yields clean JSON under
--json. Wired structured JSON output into the connectors commands
(list-available, initiate, pull, push); the sandbox commands already emit
JSON and now produce it pure. Pre-existing `logs --json` benefits too.

Tests: pure-JSON stdout assertions for sandbox + connectors list-available
+ initiate. typecheck/lint/knip clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat(cli): generic --json fallback for commands without native JSON

Make --json a universal contract in Base44Command so every command emits
valid JSON on stdout, even ones that don't build a machine payload:

- success: a command that sets result.stdout gets it verbatim (native JSON,
  status to stderr); otherwise the human status line is wrapped as
  { "output": "<text>" } (ANSI stripped).
- failure: any command emits a JSON error envelope on stdout —
  { "error", "code"?, "details"?, "hints"? } from the CLIError fields.

So `base44 whoami --json` -> {"output":"Logged in as: ..."} and a failing
`base44 sandbox list-directory --json` (no app id) -> {"error":"No Base44
app ID found.","code":"...","hints":[...]} instead of empty stdout.

Native/structured output (sandbox, connectors) is kept — it's richer than
the wrapped-status fallback (e.g. initiate still exposes redirectUrl /
connectionId as fields).

Tests: whoami --json (fallback wrap) and sandbox --json error envelope.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: document the global --json flag (machine output + silent mode)

- README: add a "Global flags" section covering --app-id and --json, with
  the contract (pure JSON stdout, silent mode, JSON error envelope,
  universal) and sandbox/jq examples.
- AGENTS.md/CLAUDE.md: note that --json forces silent mode in the
  @clack/prompts rule, and add a rule so new commands keep stdout
  machine-parseable (return RunCommandResult.stdout, status via
  outroMessage/log, emit JSON when ctx.jsonMode).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* refactor(cli): shorten sandbox subcommand names

The sandbox namespace already supplies the file/shell context, so the
redundant nouns on each subcommand can be dropped to match the CLI's
one-word-where-possible naming convention:

  list-directory -> ls
  read-file      -> read
  write-file     -> write
  edit-file      -> edit
  run-command    -> run

grep and release are already concise and unchanged. The scope itself
stays `sandbox` to keep the CLI aligned with the platform vocabulary
(the sandbox:write OAuth scope, backend, and error hints).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ew3Z6LjEgToj2bZyQHMQb

* refactor(cli): remove the sandbox release command

The sandbox release command is no longer needed. Removes the command,
its API client function, response schema, test, and README entry.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H5MJy3X1QEiXo2NFTD5Hpx

* feat(cli): add sandbox checkpoint command

Adds `base44 sandbox checkpoint` to create a restore-point checkpoint of
an app's remote sandbox via the create_checkpoint sandbox-bridge tool.
Takes an optional --name (message/title; defaults to an auto-generated
title) and returns the checkpoint id, name, and git commit hash.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H5MJy3X1QEiXo2NFTD5Hpx

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>